Facilitating integration of collaborative communication platform and document collaboration tool

ABSTRACT

Disclosed are some implementations of systems, apparatus, methods and computer program products for integrating a collaborative communication system and a document collaboration system. A document within the document collaboration system may be linked to an object within the collaborative communication system. A user post may be received in association with the object or the document. A first feed configured to be rendered in association with the object is synchronized with a second feed configured to be rendered in association with the document such that both the first feed and the second feed each includes the user post.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the United States Patent and Trademark Office patent file or records but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

This patent document generally relates to integrating a collaborative communication platform and a document collaboration tool. More specifically, this patent document discloses techniques for implementing a link between an object within the collaborative communication platform and a document maintained within the document collaboration tool.

BACKGROUND

“Cloud computing” services provide shared resources, applications, and information to computers and other devices upon request. In cloud computing environments, data can be provided by servers via the Internet rather than relying on data available locally on in-house computer systems. As such, users can interact with cloud computing services to undertake a wide range of tasks.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only to provide examples of possible structures and operations for the disclosed inventive systems, apparatus, methods and computer program products. These drawings in no way limit any changes in form and detail that may be made by one skilled in the art without departing from the spirit and scope of the disclosed implementations.

FIG. 1 shows an example of an integrated system 100, in accordance with some implementations.

FIG. 2 shows an example of integrated system 100 updating feeds, in accordance with some implementations.

FIG. 3 shows an example of a feed 300 presented via a collaborative communication system, in accordance with some implementations.

FIG. 4 shows an example of a UI 400 for integrating a collaborative communication system and a document collaboration system, in accordance with some implementations.

FIG. 5 shows a flowchart of an example of a method 500 for integrating a collaborative communication system and a document management system.

FIG. 6A shows a block diagram of an example of an environment 10 in which an on-demand database service can be used in accordance with some implementations.

FIG. 6B shows a block diagram of an example of some implementations of elements of FIG. 6A and various possible interconnections between these elements.

FIG. 7A shows a system diagram of an example of architectural components of an on-demand database service environment 900, in accordance with some implementations.

FIG. 7B shows a system diagram further illustrating an example of architectural components of an on-demand database service environment, in accordance with some implementations.

DETAILED DESCRIPTION

Examples of systems, apparatus, methods and computer program products according to the disclosed implementations are described in this section. These examples are being provided solely to add context and aid in the understanding of the disclosed implementations. It will thus be apparent to one skilled in the art that implementations may be practiced without some or all of these specific details. In other instances, certain operations have not been described in detail to avoid unnecessarily obscuring implementations. Other applications are possible, such that the following examples should not be taken as definitive or limiting either in scope or setting.

In the following detailed description, references are made to the accompanying drawings, which form a part of the description and in which are shown, by way of illustration, specific implementations. Although these implementations are described in sufficient detail to enable one skilled in the art to practice the disclosed implementations, it is understood that these examples are not limiting, such that other implementations may be used and changes may be made without departing from their spirit and scope. For example, the operations of methods shown and described herein are not necessarily performed in the order indicated. It should also be understood that the methods may include more or fewer operations than are indicated. In some implementations, operations described herein as separate operations may be combined. Conversely, what may be described herein as a single operation may be implemented in multiple operations.

A collaborative communication system is an online collaborative communication platform that enables employees of an organization to access database records pertaining to business opportunities or other business interests, as well as communicate regarding those business opportunities or business interests. Often, employees wish to collaborate on a document pertaining to a particular business opportunity or business interest. However, document collaboration is typically supported by a document collaboration system that is independent from (e.g., external to) the collaborative communication system. Unfortunately, employees collaborating on the document will be unaware of recent updates pertaining to the related business opportunity within the collaborative communication system. Similarly, employees accessing the business opportunity on the collaborative communication system will be unaware of the most recent information pertaining to the related document maintained by the document collaboration system. As a result, with conventional systems, employees often have to repeatedly switch contexts to access the separate systems if they wish to remain current on the business opportunity and the associated document.

Various implementations described or referenced herein are directed to different methods, apparatus, systems, and computer program products for facilitating the integration of a collaborative communication system with a document collaboration system. A link between an object of the collaborative communication system and a document within the document collaboration system may be generated in response to user input. Once a link between the object and the document is established, associated updates may be automatically shared between the document collaboration system and the collaborative communication system.

In accordance with various implementations, the link may be a bidirectional link. In other implementations, the link may be a unidirectional link. In response to an update to an object in the collaborative communication system or an associated feed, the update may be automatically reflected in a feed presented by the document collaboration system in association with the document. Similarly, where an update to a document or associated feed occurs, the update may be automatically reflected in a feed presented in association with the object.

An object can include a record or group of records in a database. An object can pertain to a business opportunity or project, a business group, a company, a product, or other entity.

An update to an object can include a modification to associated records. For example, an update to an object can include a new record, the deletion of a record, Similarly, an update to an object can include a modification to field(s) of a record. In some implementations, an update to an object can include a user post to an associated feed. Information pertaining to the update to the object can include an identity of a user that has updated the object, a date that the object was updated, and/or a time that the object was updated.

A document can include a digital document that is generated or maintained by a document management system. For example, the document can include an article, text, an image, a photograph, a file, a spreadsheet, a table, etc. As another example, the document can include a web page. As yet another example, a document can include a record or group of records in a database. A document can be created in response to user input. Once created, the document can be updated by the same user and/or other users who have access to the document.

An update to a document can include any modification to the document. For example, the update can include generation of the document, deletion of the document, an added field to the document, a deleted field of the document, and/or text that has been added to the document. In some implementations, an update to a document can include a user post to an associated feed. Information pertaining to the update to the document can include an identity of a user that has updated the document, a date that the document was updated, and/or a time that the document was updated.

By way of illustration, John is an employee at an organization, Pyramid Construction, Inc. John logs in to the organization and uses a collaborative communication system, which enables employees of the organization to access information regarding business opportunities, as well as communicate regarding business opportunities. John accesses a user interface (UI) to link a business opportunity, XYZ, with a document pertaining to XYZ that is available from a document collaboration system. John submits a user post regarding XYZ on the collaborative communication platform, and the user post is automatically posted in a feed presented via the document collaboration system in relation to the document. Another employee, George, submits a user post regarding the document via the document collaboration system, and the user post is automatically posted in a feed presented via the collaborative communication platform in relation to XYZ. The disclosed techniques may be applied to integrate a collaborative communication platform and a document collaboration system, as will be described in further detail below.

FIG. 1 shows an example of an integrated system 100, in accordance with some implementations. Integrated system 100 includes collaborative communication system 104 and document collaboration system 106. Collaborative communication system 104 may maintain records associated with objects in one or more databases. Example objects include, but are not limited to, companies, business opportunities, accounts, tickets, and invoices.

In some implementations, collaborative communication system 104 may enforce a permissions configuration for accessing the objects. Different entities may be provided with permission to own, edit, or access the various objects. The permissions configuration for an object may be determined at least in part based on the permissions configuration for users within a social networking system.

Collaborative communication system 104 enables users to communicate with one another regarding objects to which they have access. For example, collaborative communication system 104 may present a web page associated with an object. The user may access data pertaining to field(s) of database record(s) pertaining to the object via the web page. In addition, the web page may provide a mechanism that enables the users to communicate with one another regarding the object. Such a mechanism may include an information feed, as will be described in further detail below.

Document collaboration system 106 may maintain documents in one or more databases. Document collaboration system 106 may provide a web-based document editing utility that allows direct modification of documents. In this way, the contents of the documents may be edited directly via a web browser, and updates to the documents may be immediately shared with other users.

In addition, document collaboration system 106 enables users to communicate with one another regarding documents to which they have access. Document collaboration system 106 may provide a digital interface for collaborating on a document. For instance, one user may upload a document, while another user may edit the document. If a document is shared with a group of users, then members of the group may be granted access to the document by virtue of the sharing operation.

In some implementations, document collaboration system 106 may present a web page associated with a document. In some implementations, the user may access field(s) of database record(s) pertaining to the document via the web page. In addition, the web page may provide an information feed or other mechanism that enables the users to communicate with one another regarding the document, as will be described in further detail below.

Collaborative communication system 104 and document collaboration system 106 may be maintained by the same organization or independent organizations. Therefore, collaborative communication system 104 and document collaboration system 106 may access different databases or share the same databases.

In accordance with various implementations, an object 108 maintained by collaborative communication system 104 may be linked to a document 110 maintained by document collaboration system 106. Collaborative communication system 104 can provide updates associated with object 108 to document collaboration system 106, either directly or indirectly, via an application programming interface (API) of document collaboration system 106. In addition, document collaboration system 106 can provide updates associated with document 110 to collaborative communication system 104, directly or indirectly, via an API of collaborative communication system 104.

FIG. 2 shows an example of integrated system 100 updating feeds, in accordance with some implementations. Collaborative communication system 104 and document collaboration system 106 may independently publish updates to objects and documents, respectively. As shown in this example, collaborative communication system 104 may publish updates to an object via web feed, feed 102, which may be used to facilitate digital conversations regarding the object. Similarly, document collaboration system 106 may publish updates to a document via web feed, feed 2 204, which may be used to facilitate digital conversations regarding the document.

A user may access feed 202 by logging into collaborative communication system 104 and accessing object 108. A user may access object 108 by accessing a corresponding web page presented by collaborative communication system 104. For example, the user may click on a hypertext link presented by collaborative communication system 104.

Similarly, a user may access feed 204 by logging into document collaboration system 106 and accessing document 110. For example, a user may access document 110 via a corresponding web page presented by document collaboration system 106.

Each feed allows a user to track the progress of the corresponding database record(s). Updates to the record, also referred to herein as changes, can occur and be noted on an information feed. With the disclosed embodiments, updates are often presented as an item or entry in the feed. Types of such updates can include field changes in a data record, posts such as explicit text or characters submitted by a user, status updates, uploaded files, and links to other data or records. Also, one type of update is the creation of a record itself. Those users that are following the record or who have access to the record may view updates on the corresponding feed. The access may include viewing, editing, sharing, updating, publishing, or performing any other operations related to the associated records. The access may be provided in the context of a network.

Implementations of the disclosed systems, apparatus, and methods are configured to integrate a document collaboration system 106 with a collaborative communication system 104. More particularly, feed updates may be shared between collaborative communication system 104 and document collaboration system 106. Updates to feed 202 may be replicated in feed 204. For example, user post 206 submitted via collaborative communication system 104 may be presented in both feed 1 202 of collaborative communication system 104 and feed 2 204 of document collaboration system 106. Similarly, updates to feed 2 204 may be replicated in feed 1 202. For example, user post 208 submitted via document collaboration system 106 may be presented in both feed 2 204 of document collaboration system 106 and feed 1 202 of collaborative communication system 104. In some implementations, feed 204 is presented in a “collaboration sidebar” of document 110.

A user post may include text submitted by a user. In some implementations, a user post may further include a document that is posted by the user. For example, the document may be posted as an attachment to a message including the text. In some implementations, the attached document may be uploaded from a client machine or retrieved from a network location.

FIG. 3 shows an example of a feed 300 presented via a collaborative communication system, in accordance with some implementations. In this example, the object to which feed 300 pertains is a business opportunity, “Advanced Communications—Services 80K.” Feed 300 includes user posts pertaining to the business opportunity. Feed 300 can also include updates to fields of a record pertaining to the business opportunity. In addition, as described herein, feed 300 can replicate information presented by document collaboration system in association with a document related to the business opportunity.

FIG. 4 shows an example of a UI 400 for integrating a collaborative communication system and a document collaboration system, in accordance with some implementations. As shown in this example, a user can access a document 410 via document collaboration system 106. Document collaboration system 106 may present a feed 420 in conjunction with document 410. As shown in this example, document 410 and feed 420 both pertain to the business opportunity, “Advanced Communications—Services 80K” of FIG. 3. Feed 420 may include one or more feed items. More particularly, feed 420 may include user posts that have been submitted via document collaboration system 106, as well as user posts that have been submitted via collaborative communication system 104, as described herein. Feed 420 may further indicate updates to document 410. In accordance with various implementations, feed 420 may further include updates to a record storing data pertaining to the business opportunity, which are shared by collaborative communication system 104 with document collaboration system 106.

A user may initiate the generation of a link between an object and document. In accordance with some implementations, the user may initiate the generation of a link via a web page, which may be presented via collaborative communication system 104 or document management system 106. In some implementations, the user may specify or otherwise indicate a document identifier and object identifier. For example, a document or object identifier may include a numerical identifier or other text. In other implementations, the user may indicate a document identifier and/or object identifier using a drag-and-drop operation or menu selection. For example, the user may drag-and-drop the document to a web page pertaining to a business opportunity or other object. As another example, the user may attach the document to an electronic mail message pertaining to the object.

In some implementations, integration of collaborative communication system 104 and document management system 106 is facilitated by software that is independent from collaborative communication system. For example, the software may be accessed and downloaded from a web site such as an application store. As another example, the software may be accessed and downloaded from a web page accessed via a hypertext link or uniform resource locator (URL). The software may interface with an API of collaborative communication system 104 and an API of document management system 106.

FIG. 5 shows a flowchart of an example of a method 500 for integrating a collaborative communication system and a document management system. User input initiating the generation of a document-object link may be received at 502. The user input may indicate an identity of an object that corresponds to a record stored in a database of a collaborative communication system and an identity of a document accessible from a document collaboration system. The user input may explicitly and/or implicitly identify both the object and the document. Thus, the input may indicate a request to generate a link between the object and the document. The input may be received via the collaborative communication system, the document collaboration system, or another independent software module. For example, the user input may include a drag-and-drop operation, a document identifier, a document name, an object identifier, an object name, and/or a web link.

Responsive to the user input, a link between the object and the document may be generated and stored at 504. The link may be unidirectional or bidirectional. The link may be stored as metadata within a database of the collaborative communication system or the document management system. For example, the link may include a pointer or other metadata that associates the object with the document.

A user post submitted by a user in association with the object may be received at 506. Responsive to receiving the user post, a first feed configured to be rendered in association with the object is synchronized with a second feed configured to be rendered in association with the document at 508. More particularly, the first feed may be updated such that it includes the user post. The user post may be provided at 510 for display within the first feed via a display device.

Any other users who access the object may be presented the first feed, which includes the user post. Similarly, a user accessing the document via the document collaboration system may be presented the second feed, which includes the user post submitted via the collaborative communication system.

In further implementations, feed synchronization includes communicating object updates to the document collaboration system. Thus, an update to the object may be reflected in the first feed provided by the collaborative communication system and the second feed provided by the document collaboration tool. For example, a change in a value of a record of the collaborative communication system may be reflected in the second feed provided by the document collaboration system.

In some implementations, the second user feed may be updated via an API of the document collaboration system. For example, the user post or link thereto may be provided as a parameter of the API to the document collaboration system. As another example, a field of a data record, information pertaining to an update to the data record, or a link to the data record may be provided to the document collaboration system. As described herein, the collaborative communication system or independent software module may communicate with the API of the document collaboration system.

User posts submitted in relation to the document via the document collaboration system may similarly be replicated in the first feed provided by the collaborative communication system. In some implementations, the collaborative communication system receives a second user post or link to the second user post that has been submitted via the document collaboration tool. For example, the second user post or associated link may be received via an API of the collaborative communication system. The collaborative communication system may then update the first feed such that the first feed includes the second user post.

In accordance with various implementations, updates to the document maintained by document collaboration system may be reflected in the first feed provided by the collaborative communication system. In some implementations, the collaborative communication system receives information pertaining to update(s) to the document from the document collaboration system or an independent software module. For example, the document update(s) or link thereto may be received via an API of the collaborative communication system. The collaborative communication system may then update the first feed such that the first feed includes the information pertaining to the document update(s).

Various embodiments described or referenced herein are directed to different methods, apparatus, systems, and computer program products for facilitating the publication of updates regarding documents and associated objects within an information feed in an on-demand database service environment.

Some but not all of the techniques described or referenced herein are implemented using or in conjunction with a customer relationship management (CRM) system or other database management system. CRM systems have become a popular way to manage and analyze customer interactions and data throughout the business lifecycle. Salesforce.com, Inc. is a provider of CRM services and other database management services, any of which can be accessed and used in conjunction with the techniques disclosed herein in some implementations. In some but not all implementations, these various services can be provided in a cloud computing environment, for example, in the context of a multi-tenant database system. Thus, the disclosed techniques can be implemented without having to install software locally, that is, on computing devices of users interacting with services available through the cloud.

Some CRM systems can be implemented in various settings, including organizations. For instance, a CRM system can be implemented to provide database access to users within an enterprise such as a company or business partnership, or a group of users within such an organization. For instance, employee users in a division of a business organization may share data with users in another division of the business organization. In the example of a multi-tenant database system, each organization or group within the organization can be a respective tenant of the system, as described in greater detail below. In some but not all implementations, the disclosed methods, apparatus, systems, and computer program products may be configured or designed for use in a multi-tenant database environment.

The term “multi-tenant database system” generally refers to those systems in which various elements of hardware and/or software of a database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows of data such as customer sales data for a potentially much greater number of customers.

Where there are multiple tenants, a user is typically associated with a particular tenant. For example, a user could be a salesperson of a company, which is a tenant of the database system that provides a database service.

In some implementations, data objects in the form of CRM records such as cases, accounts, or opportunities are stored in a database system. Updates to a record may include any change to a record. Examples of record updates include field changes in the record, updates to the status of a record, as well as the creation or deletion of the record itself.

The term “record” generally refers to a data entity having fields with values and stored in database system. An example of a record is an instance of a data object created by a user of the database service, for example, in the form of a CRM record about a particular (actual or potential) business relationship or project. The record can have a data structure defined by the database service (a standard object) or defined by a user (custom object). For example, a record can be for a business partner or potential business partner (e.g., a client, vendor, distributor, etc.) of the user, and can include information describing an entire company, subsidiaries, or contacts at the company. As another example, a record can be a project that the user is working on, such as an opportunity (e.g., a possible sale) with an existing partner, or a project that the user is trying to get.

In one implementation of a multi-tenant database system, each record for the tenants has a unique identifier stored in a common table. A record has data fields that are defined by the structure of the object (e.g., fields of certain data types and purposes). A record can also have custom fields defined by a user. A field can be another record or include links thereto, thereby providing a parent-child relationship between the records.

A record can also have a status, the update of which can be provided by an owner of the record or other users having suitable write access permissions to the record. The owner can be a single user, multiple users, or a group.

In various implementations, an event can be an update of a record and/or can be triggered by a specific action by a user. Which actions trigger an event can be configurable.

Some non-limiting examples of systems, apparatus, and methods are described below for implementing database systems and enterprise level networking systems in conjunction with the disclosed techniques. Such implementations can provide more efficient use of a database system. Data may be synchronized between a database system of a primary organization and a database system of a secondary organization. Data synchronization may be suspended and resumed, as described above.

FIG. 6A shows a block diagram of an example of an environment 10 in which an on-demand database service exists and can be used in accordance with some implementations. Environment 10 may include user systems 12, network 14, database system 16, processor system 17, application platform 18, network interface 20, tenant data storage 22, system data storage 24, program code 26, and process space 28. In other implementations, environment 10 may not have all of these components and/or may have other components instead of, or in addition to, those listed above.

A user system 12 may be implemented as any computing device(s) or other data processing apparatus such as a machine or system used by a user to access a database system 16. For example, any of user systems 12 can be a handheld and/or portable computing device such as a mobile phone, a smartphone, a laptop computer, or a tablet. Other examples of a user system include computing devices such as a work station and/or a network of computing devices. As illustrated in FIG. 6A (and in more detail in FIG. 6B) user systems 12 might interact via a network 14 with an on-demand database service, which is implemented in the example of FIG. 6A as database system 16.

An on-demand database service, implemented using system 16 by way of example, is a service that is made available to users who do not need to necessarily be concerned with building and/or maintaining the database system. Instead, the database system may be available for their use when the users need the database system, i.e., on the demand of the users. Some on-demand database services may store information from one or more tenants into tables of a common database image to form a multi-tenant database system (MTS). A database image may include one or more database objects. A relational database management system (RDBMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system. In some implementations, application platform 18 enables creating, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12, or third party application developers accessing the on-demand database service via user systems 12.

The users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, when a salesperson is using a particular user system 12 to interact with system 16, the user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level, also called authorization.

Network 14 is any network or combination of networks of devices that communicate with one another. For example, network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. Network 14 can include a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the Internet. The Internet will be used in many of the examples herein. However, it should be understood that the networks that the present implementations might use are not so limited.

User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP signals to and from an HTTP server at system 16. Such an HTTP server might be implemented as the sole network interface 20 between system 16 and network 14, but other techniques might be used as well or instead. In some implementations, the network interface 20 between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least for users accessing system 16, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.

In one implementation, system 16, shown in FIG. 6A, implements a web-based CRM system. For example, in one implementation, system 16 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, web pages and other information to and from user systems 12 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object in tenant data storage 22, however, tenant data typically is arranged in the storage medium(s) of tenant data storage 22 so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain implementations, system 16 implements applications other than, or in addition to, a CRM application. For example, system 16 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 18, which manages creation of applications, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 16.

One arrangement for elements of system 16 is shown in FIGS. 6A and 6B, including a network interface 20, application platform 18, tenant data storage 22 for tenant data 23, system data storage 24 for system data 25 accessible to system 16 and possibly multiple tenants, program code 26 for implementing various functions of system 16, and a process space 28 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 16 include database indexing processes.

Several elements in the system shown in FIG. 6A include conventional, well-known elements that are explained only briefly here. For example, each user system 12 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. The term “computing device” is also referred to herein simply as a “computer.” User system 12 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 12 to access, process and view information, pages and applications available to it from system 16 over network 14. Each user system 12 also typically includes one or more user input devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a GUI provided by the browser on a display (e.g., a monitor screen, LCD display, OLED display, etc.) of the computing device in conjunction with pages, forms, applications and other information provided by system 16 or other systems or servers. Thus, “display device” as used herein can refer to a display of a computer system such as a monitor or touch-screen display, and can refer to any computing device having display capabilities such as a desktop computer, laptop, tablet, smartphone, a television set-top box, or wearable device such Google Glass® or other human body-mounted display apparatus. For example, the display device can be used to access data and applications hosted by system 16, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, implementations are suitable for use with the Internet, although other networks can be used instead of or in addition to the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one implementation, each user system 12 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 16 (and additional instances of an MTS, where more than one is present) and all of its components might be operator configurable using application(s) including computer code to run using processor system 17, which may be implemented to include a central processing unit, which may include an Intel Pentium® processor or the like, and/or multiple processor units. Non-transitory computer-readable media can have instructions stored thereon/in, that can be executed by or used to program a computing device to perform any of the methods of the implementations described herein. Computer program code 26 implementing instructions for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein is preferably downloadable and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any other type of computer-readable medium or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for the disclosed implementations can be realized in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).

According to some implementations, each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16. As such, system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to refer to one type of computing device such as a system including processing hardware and process space(s), an associated storage medium such as a memory device or database, and, in some instances, a database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database objects described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

FIG. 6B shows a block diagram of an example of some implementations of elements of FIG. 6A and various possible interconnections between these elements. That is, FIG. 6B also illustrates environment 10. However, in FIG. 6B elements of system 16 and various interconnections in some implementations are further illustrated. FIG. 6B shows that user system 12 may include processor system 12A, memory system 12B, input system 12C, and output system 12D. FIG. 6B shows network 14 and system 16. FIG. 6B also shows that system 16 may include tenant data storage 22, tenant data 23, system data storage 24, system data 25, User Interface (UI) 30, Application Program Interface (API) 32, PL/SOQL 34, save routines 36, application setup mechanism 38, application servers 50 ₁-50 _(N), system process space 52, tenant process spaces 54, tenant management process space 60, tenant storage space 62, user storage 64, and application metadata 66. In other implementations, environment 10 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system 12, network 14, system 16, tenant data storage 22, and system data storage 24 were discussed above in FIG. 6A. Regarding user system 12, processor system 12A may be any combination of one or more processors. Memory system 12B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 12C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 12D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 6B, system 16 may include a network interface 20 (of FIG. 6A) implemented as a set of application servers 50, an application platform 18, tenant data storage 22, and system data storage 24. Also shown is system process space 52, including individual tenant process spaces 54 and a tenant management process space 60. Each application server 50 may be configured to communicate with tenant data storage 22 and the tenant data 23 therein, and system data storage 24 and the system data 25 therein to serve requests of user systems 12. The tenant data 23 might be divided into individual tenant storage spaces 62, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage space 62, user storage 64 and application metadata 66 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 64. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage space 62. A UI 30 provides a user interface and an API 32 provides an application programmer interface to system 16 resident processes to users and/or developers at user systems 12. The tenant data and the system data may be stored in various databases, such as one or more Oracle® databases.

Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 54 managed by tenant management process 60 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32. A detailed description of some PL/SOQL language implementations is discussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, issued on Jun. 1, 2010, and hereby incorporated by reference in its entirety and for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 66 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server 50 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23, via a different network connection. For example, one application server 50 ₁ might be coupled via the network 14 (e.g., the Internet), another application server 50 _(N-1) might be coupled via a direct network link, and another application server 50 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 50 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain implementations, each application server 50 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 50. In one implementation, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 50 and the user systems 12 to distribute requests to the application servers 50. In one implementation, the load balancer uses a least connections algorithm to route user requests to the application servers 50. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain implementations, three consecutive requests from the same user could hit three different application servers 50, and three requests from different users could hit the same application server 50. In this manner, by way of example, system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc. can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant-specific data, system 16 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

In certain implementations, user systems 12 (which may be client systems) communicate with application servers 50 to request and/or update system-level or tenant-level data from system 16, which may involve sending one or more queries to tenant data storage 22 and/or system data storage 24. System 16 (e.g., an application server 50 in system 16) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 24 may generate query plans to access the requested data from the database.

Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects according to some implementations. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data (e.g., data item) for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for case, account, contact, lead, and opportunity data objects, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. Commonly assigned U.S. Pat. No. 7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM, by Weissman et al., issued on Aug. 17, 2010, and hereby incorporated by reference in its entirety and for all purposes, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain implementations, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.

FIG. 7A shows a system diagram of an example of architectural components of an on-demand database service environment 900, in accordance with some implementations. A client machine located in the cloud 904, generally referring to one or more networks in combination, as described herein, may communicate with the on-demand database service environment via one or more edge routers 908 and 912. A client machine can be any of the examples of user systems 12 described above. The edge routers may communicate with one or more core switches 920 and 924 via firewall 916. The core switches may communicate with a load balancer 928, which may distribute server load over different pods, such as the pods 940 and 944. The pods 940 and 944, which may each include one or more servers and/or other computing resources, may perform data processing and other operations used to provide on-demand services. Communication with the pods may be conducted via pod switches 932 and 936. Components of the on-demand database service environment may communicate with a database storage 956 via a database firewall 948 and a database switch 952.

As shown in FIGS. 7A and 7B, accessing an on-demand database service environment may involve communications transmitted among a variety of different hardware and/or software components. Further, the on-demand database service environment 900 is a simplified representation of an actual on-demand database service environment. For example, while only one or two devices of each type are shown in FIGS. 7A and 7B, some implementations of an on-demand database service environment may include anywhere from one to many devices of each type. Also, the on-demand database service environment need not include each device shown in FIGS. 7A and 7B, or may include additional devices not shown in FIGS. 7A and 7B.

Moreover, one or more of the devices in the on-demand database service environment 900 may be implemented on the same physical device or on different hardware. Some devices may be implemented using hardware or a combination of hardware and software. Thus, terms such as “data processing apparatus,” “machine,” “server” and “device” as used herein are not limited to a single hardware device, but rather include any hardware and software configured to provide the described functionality.

The cloud 904 is intended to refer to a data network or combination of data networks, often including the Internet. Client machines located in the cloud 904 may communicate with the on-demand database service environment to access services provided by the on-demand database service environment. For example, client machines may access the on-demand database service environment to retrieve, store, edit, and/or process information.

In some implementations, the edge routers 908 and 912 route packets between the cloud 904 and other components of the on-demand database service environment 900. The edge routers 908 and 912 may employ the Border Gateway Protocol (BGP). The BGP is the core routing protocol of the Internet. The edge routers 908 and 912 may maintain a table of IP networks or ‘prefixes’, which designate network reachability among autonomous systems on the Internet.

In one or more implementations, the firewall 916 may protect the inner components of the on-demand database service environment 900 from Internet traffic. The firewall 916 may block, permit, or deny access to the inner components of the on-demand database service environment 900 based upon a set of rules and other criteria. The firewall 916 may act as one or more of a packet filter, an application gateway, a stateful filter, a proxy server, or any other type of firewall.

In some implementations, the core switches 920 and 924 are high-capacity switches that transfer packets within the on-demand database service environment 900. The core switches 920 and 924 may be configured as network bridges that quickly route data between different components within the on-demand database service environment. In some implementations, the use of two or more core switches 920 and 924 may provide redundancy and/or reduced latency.

In some implementations, the pods 940 and 944 may perform the core data processing and service functions provided by the on-demand database service environment. Each pod may include various types of hardware and/or software computing resources. An example of the pod architecture is discussed in greater detail with reference to FIG. 7B.

In some implementations, communication between the pods 940 and 944 may be conducted via the pod switches 932 and 936. The pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and client machines located in the cloud 904, for example via core switches 920 and 924. Also, the pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and the database storage 956.

In some implementations, the load balancer 928 may distribute workload between the pods 940 and 944. Balancing the on-demand service requests between the pods may assist in improving the use of resources, increasing throughput, reducing response times, and/or reducing overhead. The load balancer 928 may include multilayer switches to analyze and forward traffic.

In some implementations, access to the database storage 956 may be guarded by a database firewall 948. The database firewall 948 may act as a computer application firewall operating at the database application layer of a protocol stack. The database firewall 948 may protect the database storage 956 from application attacks such as structure query language (SQL) injection, database rootkits, and unauthorized information disclosure.

In some implementations, the database firewall 948 may include a host using one or more forms of reverse proxy services to proxy traffic before passing it to a gateway router. The database firewall 948 may inspect the contents of database traffic and block certain content or database requests. The database firewall 948 may work on the SQL application level atop the TCP/IP stack, managing applications' connection to the database or SQL management interfaces as well as intercepting and enforcing packets traveling to or from a database network or application interface.

In some implementations, communication with the database storage 956 may be conducted via the database switch 952. The multi-tenant database storage 956 may include more than one hardware and/or software components for handling database queries. Accordingly, the database switch 952 may direct database queries transmitted by other components of the on-demand database service environment (e.g., the pods 940 and 944) to the correct components within the database storage 956.

In some implementations, the database storage 956 is an on-demand database system shared by many different organizations. The on-demand database service may employ a multi-tenant approach, a virtualized approach, or any other type of database approach. On-demand database services are discussed in greater detail with reference to FIG. 7B.

FIG. 7B shows a system diagram further illustrating an example of architectural components of an on-demand database service environment, in accordance with some implementations. The pod 944 may be used to render services to a user of the on-demand database service environment 900. In some implementations, each pod may include a variety of servers and/or other systems. The pod 944 includes one or more content batch servers 964, content search servers 968, query servers 982, file servers 986, access control system (ACS) servers 980, batch servers 984, and app servers 988. Also, the pod 944 includes database instances 990, quick file systems (QFS) 992, and indexers 994. In one or more implementations, some or all communication between the servers in the pod 944 may be transmitted via the switch 936.

The content batch servers 964 may handle requests internal to the pod. These requests may be long-running and/or not tied to a particular customer. For example, the content batch servers 964 may handle requests related to log mining, cleanup work, and maintenance tasks.

The content search servers 968 may provide query and indexer functions. For example, the functions provided by the content search servers 968 may allow users to search through content stored in the on-demand database service environment.

The file servers 986 may manage requests for information stored in the file storage 998. The file storage 998 may store information such as documents, images, and basic large objects (BLOBs). By managing requests for information using the file servers 986, the image footprint on the database may be reduced.

The query servers 982 may be used to retrieve information from one or more file systems. For example, the query system 982 may receive requests for information from the app servers 988 and then transmit information queries to the NFS 996 located outside the pod.

The pod 944 may share a database instance 990 configured as a multi-tenant environment in which different organizations share access to the same database. Additionally, services rendered by the pod 944 may call upon various hardware and/or software resources. In some implementations, the ACS servers 980 may control access to data, hardware resources, or software resources.

In some implementations, the batch servers 984 may process batch jobs, which are used to run tasks at specified times. Thus, the batch servers 984 may transmit instructions to other servers, such as the app servers 988, to trigger the batch jobs.

In some implementations, the QFS 992 may be an open source file system available from Sun Microsystems® of Santa Clara, Calif. The QFS may serve as a rapid-access file system for storing and accessing information available within the pod 944. The QFS 992 may support some volume management capabilities, allowing many disks to be grouped together into a file system. File system metadata can be kept on a separate set of disks, which may be useful for streaming applications where long disk seeks cannot be tolerated. Thus, the QFS system may communicate with one or more content search servers 968 and/or indexers 994 to identify, retrieve, move, and/or update data stored in the network file systems 996 and/or other storage systems.

In some implementations, one or more query servers 982 may communicate with the NFS 996 to retrieve and/or update information stored outside of the pod 944. The NFS 996 may allow servers located in the pod 944 to access information to access files over a network in a manner similar to how local storage is accessed.

In some implementations, queries from the query servers 922 may be transmitted to the NFS 996 via the load balancer 928, which may distribute resource requests over various resources available in the on-demand database service environment. The NFS 996 may also communicate with the QFS 992 to update the information stored on the NFS 996 and/or to provide information to the QFS 992 for use by servers located within the pod 944.

In some implementations, the pod may include one or more database instances 990. The database instance 990 may transmit information to the QFS 992. When information is transmitted to the QFS, it may be available for use by servers within the pod 944 without using an additional database call.

In some implementations, database information may be transmitted to the indexer 994. Indexer 994 may provide an index of information available in the database 990 and/or QFS 992. The index information may be provided to file servers 986 and/or the QFS 992.

In some implementations, one or more application servers or other servers described above with reference to FIGS. 8A and 8B include a hardware and/or software framework configurable to execute procedures using programs, routines, scripts, etc. Thus, in some implementations, one or more of application servers 50 ₁-50 _(N) of FIG. 6B can be configured to initiate performance of one or more of the operations described above with reference to FIGS. 1A-7D by instructing another computing device to perform an operation. In some implementations, one or more application servers 50 ₁-50 _(N) carry out, either partially or entirely, one or more of the disclosed operations described with reference to FIGS. 1A-7D. In some implementations, app servers 988 of FIG. 7B support the construction of applications provided by the on-demand database service environment 900 via the pod 944. Thus, an app server 988 may include a hardware and/or software framework configurable to execute procedures to partially or entirely carry out or instruct another computing device to carry out one or more operations disclosed herein, including operations described above with reference to FIG. 5 In alternative implementations, two or more app servers 988 may cooperate to perform or cause performance of such operations. Any of the databases and other storage facilities described above with reference to FIGS. 6A, 6B, 7A and 7B can be configured to store lists, articles, documents, records, files, and other objects for implementing the operations described above with reference to FIG. 5. For instance, lists of published fields associated with corresponding connections can be maintained in tenant data storage 22 and/or system data storage 24 of FIGS. 6A and 6B. In some other implementations, rather than storing one or more lists, articles, documents, records, and/or files, the databases and other storage facilities described above can store pointers to the lists, articles, documents, records, and/or files, which may instead be stored in other repositories external to the systems and environments described above with reference to FIGS. 6A, 6B, 7A and 7B.

While some of the disclosed implementations may be described with reference to a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the disclosed implementations are not limited to multi-tenant databases nor deployment on application servers. Some implementations may be practiced using various database architectures such as ORACLE®, DB2® by IBM and the like without departing from the scope of the implementations claimed.

It should be understood that some of the disclosed implementations can be embodied in the form of control logic using hardware and/or computer software in a modular or integrated manner. Other ways and/or methods are possible using hardware and a combination of hardware and software.

Any of the disclosed implementations may be embodied in various types of hardware, software, firmware, and combinations thereof. For example, some techniques disclosed herein may be implemented, at least in part, by computer-readable media that include program instructions, state information, etc., for performing various services and operations described herein. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher-level code that may be executed by a computing device such as a server or other data processing apparatus using an interpreter. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as flash memory, compact disk (CD) or digital versatile disk (DVD); magneto-optical media; and hardware devices specially configured to store program instructions, such as read-only memory (ROM) devices and random access memory (RAM) devices. A computer-readable medium may be any combination of such storage devices.

Any of the operations and techniques described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer-readable medium. Computer-readable media encoded with the software/program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer-readable medium may reside on or within a single computing device or an entire computer system, and may be among other computer-readable media within a system or network. A computer system or computing device may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.

While various implementations have been described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present application should not be limited by any of the implementations described herein, but should be defined only in accordance with the following and later-submitted claims and their equivalents. 

What is claimed is:
 1. A system comprising: a collaborative communication system implemented using a server system, the collaborative communication system configurable to cause: processing an indication of user input, the user input pertaining to an object that corresponds to a record stored in a database of the collaborative communication system and identifying a document accessible from a document collaboration system, the document including a file that is independent from the record, the document collaboration system providing a web-based document editing utility that facilitates collaboration on documents; responsive to processing the indication of the user input, generating and storing a link between the object and the document; processing a user post submitted by a user in association with the object; responsive to processing the user post, synchronizing a first feed configured to be rendered by the collaborative communication system in association with the object with a second feed configured to be rendered by the document collaboration system in association with the document according to the link such that both the first feed and the second feed each includes the user post; and providing the user post for display within the first feed via a display device.
 2. The system as recited in claim 1, the collaborative communication system further configurable to cause: updating the first feed such that the first feed includes the user post; and updating, via an application programming interface of the document collaboration tool, the second feed.
 3. The system as recited in claim 1, the collaborative communication system further configurable to cause: receiving, via an application programming interface (API) of the collaborative platform, a second user post or link to the second user post that has been submitted via the document collaboration tool in association with the document; and updating the first feed such that the first feed includes the second user post.
 4. The system of claim 1, wherein the input indicates a request to generate a link between the object and the document.
 5. The system of claim 1, wherein the user input comprises a drag-and-drop operation, a document identifier, a document name, or a web link.
 6. The system of claim 1, wherein the link is a bidirectional link.
 7. The system of claim 1, the collaborative communication system further configurable to cause: ascertaining that a value of a field of the record has changed; and updating the second feed such that the second feed indicates a change in the value of the field of the record.
 8. A computer program product comprising computer-readable program code capable of being executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause: processing an indication of user input, the user input pertaining to an object that corresponds to a record stored in a database of a collaborative communication system and identifying a document accessible from a document collaboration system, the document including a file that is independent from the record, the document collaboration system providing a web-based document editing utility that facilitates collaboration on documents; responsive to processing the indication of the user input, generating and storing a link between the object and the document; processing a user post submitted by a user in association with the object; responsive to processing the user post, synchronizing a first feed configured to be rendered by the collaborative communication system in association with the object with a second feed configured to be rendered by the document collaboration system in association with the document according to the link such that both the first feed and the second feed each includes the user post; and providing the user post for display within the first feed via a display device.
 9. The computer program product as recited in claim 8, the program code comprising instructions further configured to cause: updating the first feed such that the first feed includes the user post; and updating, via an application programming interface of the document collaboration tool, the second feed.
 10. The computer program product as recited in claim 8, the program code comprising instructions further configured to cause: receiving, via an application programming interface (API) of the collaborative platform, a second user post or link to the second user post that has been submitted via the document collaboration tool; and updating the first user feed such that the first feed includes the second user post.
 11. The computer program product as recited in claim 8, wherein the input indicates a request to generate a link between the object and the document.
 12. The computer program product as recited in claim 8, wherein the user input comprises a drag-and-drop operation, a document identifier, a document name, or a web link.
 13. The computer program product as recited in claim 8, wherein the link is a bidirectional link.
 14. The computer program product as recited in claim 8, the program code comprising instructions further configured to cause: ascertaining that a value of a field of the record has changed; and updating the second feed such that the second feed indicates a change in the value of the field of the record.
 15. A method, comprising: obtaining an indication of user input, the user input pertaining to an object that corresponds to a record stored in a database of a collaborative communication system and identifying a document accessible from a document collaboration system, the document including a file that is independent from the record, the document collaboration system providing a web-based document editing utility that facilitates collaboration on documents; responsive to the indication of the user input, generating and storing a link between the object and the document; processing a user post submitted by a user in association with the object; responsive to processing the user post, synchronizing a first feed configured to be rendered by the collaborative communication system in association with the object with a second feed configured to be rendered by the document collaboration system in association with the document according to the link such that both the first feed and the second feed each includes the user post; and providing the user post for display within the first feed via a display device.
 16. The method as recited in claim 15, wherein synchronizing the first feed displayed in association with the object with the second feed displayed in association with the document comprises: updating the first user feed such that the first feed includes the user post; and updating, via an application programming interface of the document collaboration tool, the second feed.
 17. The method as recited in claim 15, further comprising: receiving, via an application programming interface (API) of the collaborative platform, a second user post or link to the second user post that has been submitted via the document collaboration tool in association with the document; and updating the first feed such that the first feed includes the second user post.
 18. The method of claim 15, wherein the input indicates a request to generate a link between the object and the document.
 19. The method of claim 15, wherein the user input comprises a drag-and-drop operation, a document identifier, a document name, or a web link.
 20. The method of claim 15, further comprising: ascertaining that a value of a field of the record has changed; and updating the second feed such that the second feed indicates a change in the value of the field of the record.
 21. The method of claim 15, wherein the record comprises a customer relationship management (CRM) record. 